Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c6dd9e6895455b33d5d088f8603f346ed7bfc82de650d12154273771ee7ef6

Tx prefix hash: ab6d67d8fb54f89d8a347fd7359107421bca89eed2254309c31237b725e04ca1
Tx public key: c61e54a169cf9ae6aa074927331795d7399a28e583278efbfa6e4b523b3cfed1
Timestamp: 1699907971 Timestamp [UCT]: 2023-11-13 20:39:31 Age [y:d:h:m:s]: 01:145:17:18:40
Block: 890978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365331 RingCT/type: yes/0
Extra: 01c61e54a169cf9ae6aa074927331795d7399a28e583278efbfa6e4b523b3cfed102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.685204206000 dcy

stealth address amount amount idx
00: 348a33984e5b94b04d839cfdcdaf8ddc142c76df13ba0261781e1947f2d0f000 0.685204206000 1347013 of 0

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": 890988, "vin": [ { "gen": { "height": 890978 } } ], "vout": [ { "amount": 685204206, "target": { "key": "348a33984e5b94b04d839cfdcdaf8ddc142c76df13ba0261781e1947f2d0f000" } } ], "extra": [ 1, 198, 30, 84, 161, 105, 207, 154, 230, 170, 7, 73, 39, 51, 23, 149, 215, 57, 154, 40, 229, 131, 39, 142, 251, 250, 110, 75, 82, 59, 60, 254, 209, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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