Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 868bc60b0da4fa1cc24e6ac4c0e3cbe62d428be77cfb62dfaca439022314c430

Tx prefix hash: 3fa93307241bee0f8131de79b706192f862478eab453c1ae032e19315819393e
Tx public key: f65df1ddb1d8e5a0fe695becb5ae5fe09c0ff7de4635a31a3e2b2ff0283f7c87
Timestamp: 1614257084 Timestamp [UTC]: 2021-02-25 12:44:44 Age [y:d:h:m:s]: 05:267:09:55:27
Block: 206391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1475050 RingCT/type: yes/0
Extra: 01f65df1ddb1d8e5a0fe695becb5ae5fe09c0ff7de4635a31a3e2b2ff0283f7c8702110000003b57f0ba47000000000000000000

1 output(s) for total of 0.127101030356 xmr

stealth address amount amount idx tag
00: eafc195b6034f046f4df8b2cbcfb99687511501efed2b68a9bd23a617024f61e 0.127101030356 421697 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 dinastycoin-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": 206401, "vin": [ { "gen": { "height": 206391 } } ], "vout": [ { "amount": 127101030356, "target": { "key": "eafc195b6034f046f4df8b2cbcfb99687511501efed2b68a9bd23a617024f61e" } } ], "extra": [ 1, 246, 93, 241, 221, 177, 216, 229, 160, 254, 105, 91, 236, 181, 174, 95, 224, 156, 15, 247, 222, 70, 53, 163, 26, 62, 43, 47, 240, 40, 63, 124, 135, 2, 17, 0, 0, 0, 59, 87, 240, 186, 71, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: