Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15798e903f3a25154ae1bea28a542aab096cb35a9aed91ea0c86a9b10eed6907

Tx prefix hash: 25c1c246ee03677eafe0a00576d59d85254f8b45b3266cb75dc335bf7dec5842
Tx public key: 261a5fd265b9d4e4facc192689c86d5222208f1d8a0a2165d5e7ba7d0932681d
Timestamp: 1713186429 Timestamp [UCT]: 2024-04-15 13:07:09 Age [y:d:h:m:s]: 01:039:09:24:54
Block: 1001064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289132 RingCT/type: yes/0
Extra: 01261a5fd265b9d4e4facc192689c86d5222208f1d8a0a2165d5e7ba7d0932681d0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15ab2c2ccbdc5ca3e65f297d4b6f87bd915e2972f6381ccd6a61c96b4684e3cb 0.600000000000 1461566 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": 1001074, "vin": [ { "gen": { "height": 1001064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15ab2c2ccbdc5ca3e65f297d4b6f87bd915e2972f6381ccd6a61c96b4684e3cb" } } ], "extra": [ 1, 38, 26, 95, 210, 101, 185, 212, 228, 250, 204, 25, 38, 137, 200, 109, 82, 34, 32, 143, 29, 138, 10, 33, 101, 213, 231, 186, 125, 9, 50, 104, 29, 2, 17, 0, 0, 0, 5, 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