Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc06e76dd4001b5c90f26ba33d283f490bccbeb7740d37146257ee489c956609

Tx prefix hash: 0af39d31a2811acb1c3b4e88d1af98132b2e954f9715e84f08d3e3d7bacd6565
Tx public key: b1d15b378e0fd4f8d3ffce25ab7335a66a4175fe2d990851a5ed3c5d97fad715
Timestamp: 1736289410 Timestamp [UCT]: 2025-01-07 22:36:50 Age [y:d:h:m:s]: 00:316:23:51:09
Block: 1192464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224066 RingCT/type: yes/0
Extra: 01b1d15b378e0fd4f8d3ffce25ab7335a66a4175fe2d990851a5ed3c5d97fad715021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8209599af269651205953679067f8fdb48802f2cc2e23b1070aaaff6e0af132 0.600000000000 1679017 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": 1192474, "vin": [ { "gen": { "height": 1192464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8209599af269651205953679067f8fdb48802f2cc2e23b1070aaaff6e0af132" } } ], "extra": [ 1, 177, 209, 91, 55, 142, 15, 212, 248, 211, 255, 206, 37, 171, 115, 53, 166, 106, 65, 117, 254, 45, 153, 8, 81, 165, 237, 60, 93, 151, 250, 215, 21, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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