Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b40a79e3beebab09fca2dc4daa47b3450667cc87b787d1404346e441e955aae

Tx prefix hash: 54d62b54d8ac732be4beab35186da05ea4eaff3e2862f6b530a8d831282a97a3
Tx public key: 9eb661615301a305adfbb207f9efedb749ed250e25b1b491ff56c18fa4c2c14c
Timestamp: 1771505089 Timestamp [UTC]: 2026-02-19 12:44:49 Age [y:d:h:m:s]: 00:268:23:41:39
Block: 1481211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197678 RingCT/type: yes/0
Extra: 019eb661615301a305adfbb207f9efedb749ed250e25b1b491ff56c18fa4c2c14c021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 672e3fe0756745b2f2dea2f2405c524981ad56d4f58bce283f148c40dfd7f2ed 0.000600000000 1970587 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": 1481221, "vin": [ { "gen": { "height": 1481211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "672e3fe0756745b2f2dea2f2405c524981ad56d4f58bce283f148c40dfd7f2ed" } } ], "extra": [ 1, 158, 182, 97, 97, 83, 1, 163, 5, 173, 251, 178, 7, 249, 239, 237, 183, 73, 237, 37, 14, 37, 177, 180, 145, 255, 86, 193, 143, 164, 194, 193, 76, 2, 17, 0, 0, 0, 4, 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: