Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30bdf4dbabc49d9e5c2f0a306e2f0914efcca1cfa0b464d7313416b57d10e8ef

Tx prefix hash: 564a6a606cf863f39c83770268418457d14dd73d225c76d4abfd703f1d100004
Tx public key: eda87e9105b1e9a6d7d76e30eaf361c0057df29550bafc5e150ab026556e79d2
Timestamp: 1772593407 Timestamp [UTC]: 2026-03-04 03:03:27 Age [y:d:h:m:s]: 00:260:21:10:55
Block: 1490220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192035 RingCT/type: yes/0
Extra: 01eda87e9105b1e9a6d7d76e30eaf361c0057df29550bafc5e150ab026556e79d2021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3cfdcd2d49ba66360bd511a8f409aea1a250c80ce0b15fce9dc97b163206a2cf 0.000600000000 1979722 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": 1490230, "vin": [ { "gen": { "height": 1490220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cfdcd2d49ba66360bd511a8f409aea1a250c80ce0b15fce9dc97b163206a2cf" } } ], "extra": [ 1, 237, 168, 126, 145, 5, 177, 233, 166, 215, 215, 110, 48, 234, 243, 97, 192, 5, 125, 242, 149, 80, 186, 252, 94, 21, 10, 176, 38, 85, 110, 121, 210, 2, 17, 0, 0, 0, 2, 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: