Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44d72aa6a2f0a2b58d4572b7672f74ae327a9956d428894d3b7a8a7cd25d5277

Tx prefix hash: af031b81a737697c069b62a70f4d235ae878ef017a788d37841a634be08b42fb
Tx public key: edf1907b59711ab84897a243844de38bc5c7b1832cbac68b0f42aef5abf2c563
Timestamp: 1726498537 Timestamp [UCT]: 2024-09-16 14:55:37 Age [y:d:h:m:s]: 00:181:20:31:16
Block: 1111430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129816 RingCT/type: yes/0
Extra: 01edf1907b59711ab84897a243844de38bc5c7b1832cbac68b0f42aef5abf2c56302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cd7d452211bd64089c6b9688ae15d0b0d06b504b81f4ef09ade6555fcfce165 0.600000000000 1590387 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": 1111440, "vin": [ { "gen": { "height": 1111430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cd7d452211bd64089c6b9688ae15d0b0d06b504b81f4ef09ade6555fcfce165" } } ], "extra": [ 1, 237, 241, 144, 123, 89, 113, 26, 184, 72, 151, 162, 67, 132, 77, 227, 139, 197, 199, 177, 131, 44, 186, 198, 139, 15, 66, 174, 245, 171, 242, 197, 99, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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