Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 828eee99fc329d9a7f2d8521754e02b409cb94b6bb8420a38a75fc0e408397ce

Tx prefix hash: e27f21959b2211b73aa3c1913dc9470a874a2addfd6dc95607bd5821769e557a
Tx public key: 4142c581bf40d8881f18832d68d1e1c5cfe20c4f10874f87e0d53a80762d1e41
Timestamp: 1707408910 Timestamp [UCT]: 2024-02-08 16:15:10 Age [y:d:h:m:s]: 01:053:07:17:07
Block: 953160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299141 RingCT/type: yes/0
Extra: 014142c581bf40d8881f18832d68d1e1c5cfe20c4f10874f87e0d53a80762d1e410211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 153573590d905a22e894378e5478fa9e373974f94e774e804108d915d5d1a420 0.600000000000 1412332 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": 953170, "vin": [ { "gen": { "height": 953160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "153573590d905a22e894378e5478fa9e373974f94e774e804108d915d5d1a420" } } ], "extra": [ 1, 65, 66, 197, 129, 191, 64, 216, 136, 31, 24, 131, 45, 104, 209, 225, 197, 207, 226, 12, 79, 16, 135, 79, 135, 224, 213, 58, 128, 118, 45, 30, 65, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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