Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13d49efc6bda0211c70a4de8a26ec205e2e4213584e636973155274e5e614d6f

Tx prefix hash: d721e502a528509a2f2272d75d939767a06333e3000f535f58f2f569b6c7f727
Tx public key: 32f9717ac9934740121a6fc8c106fc705e99a36ae2d3897ebcb3ab4b39cf34b8
Timestamp: 1716588373 Timestamp [UCT]: 2024-05-24 22:06:13 Age [y:d:h:m:s]: 01:166:19:09:22
Block: 1029281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377791 RingCT/type: yes/0
Extra: 0132f9717ac9934740121a6fc8c106fc705e99a36ae2d3897ebcb3ab4b39cf34b802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd2727280b393ac5a490c66d1db9b1c4a40dcf4eacf184a85cc2eb4f1b4bc8c6 0.600000000000 1497324 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": 1029291, "vin": [ { "gen": { "height": 1029281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd2727280b393ac5a490c66d1db9b1c4a40dcf4eacf184a85cc2eb4f1b4bc8c6" } } ], "extra": [ 1, 50, 249, 113, 122, 201, 147, 71, 64, 18, 26, 111, 200, 193, 6, 252, 112, 94, 153, 163, 106, 226, 211, 137, 126, 188, 179, 171, 75, 57, 207, 52, 184, 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