Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bebcf7e368b69fcbe9906e369fc6e1380210eb9abc51ad92b4ff7884b2f84673

Tx prefix hash: 9078f973a4d5e4fe27b145252be7697e22cd309c8ac9f413ff2dc76198f5d2ab
Tx public key: c0577e42ee3ef2d56c47d13e0082e7f91bede9e1d97d207974a133918cb0a31e
Timestamp: 1771593957 Timestamp [UTC]: 2026-02-20 13:25:57 Age [y:d:h:m:s]: 00:271:02:32:15
Block: 1481946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199280 RingCT/type: yes/0
Extra: 01c0577e42ee3ef2d56c47d13e0082e7f91bede9e1d97d207974a133918cb0a31e021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ae2d80cc999f8ca2c8b5a3d8eef9a333f3be38bdc47fbdfe9afb43246314ae88 0.000600000000 1971332 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 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": 1481956, "vin": [ { "gen": { "height": 1481946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae2d80cc999f8ca2c8b5a3d8eef9a333f3be38bdc47fbdfe9afb43246314ae88" } } ], "extra": [ 1, 192, 87, 126, 66, 238, 62, 242, 213, 108, 71, 209, 62, 0, 130, 231, 249, 27, 237, 233, 225, 217, 125, 32, 121, 116, 161, 51, 145, 140, 176, 163, 30, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: