Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aded153a3500d8d9c41dc487297d0296a09431da6128740d65fa26f3f118f42

Tx prefix hash: a70c924ae1904146e2668ed665e20e76186a6b10f9faf0164f0955c6271fa82a
Tx public key: 2f9f2aac6ba7feffbc4b00d16e4cfbbd0b89d115e454187017667d74cf9ff1c1
Timestamp: 1577813034 Timestamp [UCT]: 2019-12-31 17:23:54 Age [y:d:h:m:s]: 05:038:01:44:07
Block: 35908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176920 RingCT/type: yes/0
Extra: 012f9f2aac6ba7feffbc4b00d16e4cfbbd0b89d115e454187017667d74cf9ff1c10211000000038a2ee0d9000000000000000000

1 output(s) for total of 466.683819376000 dcy

stealth address amount amount idx
00: 61af8861f62eb2d982a59b0cc11615a0176ad3af5c8bb5e8e95f7f31080ad2c1 466.683819376000 60648 of 0

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": 35918, "vin": [ { "gen": { "height": 35908 } } ], "vout": [ { "amount": 466683819376, "target": { "key": "61af8861f62eb2d982a59b0cc11615a0176ad3af5c8bb5e8e95f7f31080ad2c1" } } ], "extra": [ 1, 47, 159, 42, 172, 107, 167, 254, 255, 188, 75, 0, 209, 110, 76, 251, 189, 11, 137, 209, 21, 228, 84, 24, 112, 23, 102, 125, 116, 207, 159, 241, 193, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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