Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1966248371fa1308c53bd6322c4c1e547741518f34d7da6cbc9fc0b817831cf4

Tx prefix hash: 0fcba01588439c5327d8e84ab8fc3e21e4dfdb015bb98fb127909440d289d44a
Tx public key: f97e4cdfd95260f42a45dd63855b5e5eae3aa464c942ae1608fa89c0caaa4b06
Timestamp: 1720559582 Timestamp [UCT]: 2024-07-09 21:13:02 Age [y:d:h:m:s]: 00:253:01:03:50
Block: 1062203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180795 RingCT/type: yes/0
Extra: 01f97e4cdfd95260f42a45dd63855b5e5eae3aa464c942ae1608fa89c0caaa4b06021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1626a03c8a6333f16a3b3f403e8e61d0cf4694801b39fab80f7ccb567185bd1d 0.600000000000 1532704 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": 1062213, "vin": [ { "gen": { "height": 1062203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1626a03c8a6333f16a3b3f403e8e61d0cf4694801b39fab80f7ccb567185bd1d" } } ], "extra": [ 1, 249, 126, 76, 223, 217, 82, 96, 244, 42, 69, 221, 99, 133, 91, 94, 94, 174, 58, 164, 100, 201, 66, 174, 22, 8, 250, 137, 192, 202, 170, 75, 6, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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