Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5e1499d86d3e8d91d8774ad0508aae7857f5e8b5ad133e997363cc7c26ed42c

Tx prefix hash: 820fb430c7bddf5f22b48c0e39623c63ab23ca0090df7695f1171c83aad08ef3
Tx public key: 9f344121b96872e5306e2d393e797d62542d5d659cb185a3058c9933ee8ae4ff
Timestamp: 1718927596 Timestamp [UCT]: 2024-06-20 23:53:16 Age [y:d:h:m:s]: 01:140:16:31:14
Block: 1048660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359106 RingCT/type: yes/0
Extra: 019f344121b96872e5306e2d393e797d62542d5d659cb185a3058c9933ee8ae4ff02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3cf7a60031e917b3607e56cc35f208468f48ffce90f3a8f431c1e35877e8005 0.600000000000 1518745 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": 1048670, "vin": [ { "gen": { "height": 1048660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3cf7a60031e917b3607e56cc35f208468f48ffce90f3a8f431c1e35877e8005" } } ], "extra": [ 1, 159, 52, 65, 33, 185, 104, 114, 229, 48, 110, 45, 57, 62, 121, 125, 98, 84, 45, 93, 101, 156, 177, 133, 163, 5, 140, 153, 51, 238, 138, 228, 255, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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