Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63a6ea007eb1fb2c1c0e0d470fe5ec64772a2b52c2b0b9da0088f8caa26a3618

Tx prefix hash: 469d85e10e4b3b01f01b6a67282039cc43fdfd2a3d9b1462adacb61339b72daa
Tx public key: bd380f573557b65b2afb3d986f1c7fc22184297029e90134b833a39f13f72c78
Timestamp: 1772387879 Timestamp [UTC]: 2026-03-01 17:57:59 Age [y:d:h:m:s]: 00:262:18:21:03
Block: 1488513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193366 RingCT/type: yes/0
Extra: 01bd380f573557b65b2afb3d986f1c7fc22184297029e90134b833a39f13f72c78021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 990f45191f6c2a52652931c1f5bc3f50efcce8ebf9ebf04cae9e4c2c9fa2976d 0.000600000000 1977993 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": 1488523, "vin": [ { "gen": { "height": 1488513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "990f45191f6c2a52652931c1f5bc3f50efcce8ebf9ebf04cae9e4c2c9fa2976d" } } ], "extra": [ 1, 189, 56, 15, 87, 53, 87, 182, 91, 42, 251, 61, 152, 111, 28, 127, 194, 33, 132, 41, 112, 41, 233, 1, 52, 184, 51, 163, 159, 19, 247, 44, 120, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: