Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3af40e4824566d75dfa7ee75ea723c07183671a84cd8a4b68e111107f0db1d27

Tx prefix hash: 2c9b53bf2128db4c5433e4c3f90e46c1620bb856d532be42931d2825b3977d5c
Tx public key: f34309a378877db920e50b1eb199ebb592bb2fb3ab3e832c6ead8e70a4ba1133
Timestamp: 1705506977 Timestamp [UCT]: 2024-01-17 15:56:17 Age [y:d:h:m:s]: 01:038:17:53:50
Block: 937388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288752 RingCT/type: yes/0
Extra: 01f34309a378877db920e50b1eb199ebb592bb2fb3ab3e832c6ead8e70a4ba11330211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 498622641233ddd41c6637f4b082fae972c6d6f8343f84d50376216b5c87c4f9 0.600000000000 1395440 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 937398, "vin": [ { "gen": { "height": 937388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "498622641233ddd41c6637f4b082fae972c6d6f8343f84d50376216b5c87c4f9" } } ], "extra": [ 1, 243, 67, 9, 163, 120, 135, 125, 185, 32, 229, 11, 30, 177, 153, 235, 181, 146, 187, 47, 179, 171, 62, 131, 44, 110, 173, 142, 112, 164, 186, 17, 51, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8