Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25866268b230bb44a2551a3dd446cff995cb8875d7a77580572f83a9ace441d4

Tx prefix hash: 378f0e4237d2e9a1ec1508f9e28b74ebe3b8d5b256512bbd392c3ea163567ba7
Tx public key: a73b6b7f3a2deab529c3ea597254c6ad7719739f880eb2133c3f2ec6e541afb4
Timestamp: 1728320824 Timestamp [UCT]: 2024-10-07 17:07:04 Age [y:d:h:m:s]: 00:207:09:27:17
Block: 1126537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148038 RingCT/type: yes/0
Extra: 01a73b6b7f3a2deab529c3ea597254c6ad7719739f880eb2133c3f2ec6e541afb402110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21056ef5663ab49a525baac9b2680faa1eb1056620868daa7d5d715cf8371819 0.600000000000 1609332 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": 1126547, "vin": [ { "gen": { "height": 1126537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21056ef5663ab49a525baac9b2680faa1eb1056620868daa7d5d715cf8371819" } } ], "extra": [ 1, 167, 59, 107, 127, 58, 45, 234, 181, 41, 195, 234, 89, 114, 84, 198, 173, 119, 25, 115, 159, 136, 14, 178, 19, 60, 63, 46, 198, 229, 65, 175, 180, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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