Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47d03418cd3a371b1ed4daec716f4997dbb6822a145be875d81c64e1ad42e108

Tx prefix hash: f5a62abe3d1741821e0e486065afbbdb6d3c9d8a84790cc6b336f480f13525ef
Tx public key: d53d14e3815dbdbedb79102914d01f18783e7b5e65a71650559800912cce7512
Timestamp: 1674423240 Timestamp [UTC]: 2023-01-22 21:34:00 Age [y:d:h:m:s]: 03:301:19:28:03
Block: 680573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1001458 RingCT/type: yes/0
Extra: 01d53d14e3815dbdbedb79102914d01f18783e7b5e65a71650559800912cce75120211000000015029cbac000000000000000000

1 output(s) for total of 0.003411764716 xmr

stealth address amount amount idx tag
00: bb0c9e7b4e8b41ca1a0ec77fa4b8e13eb188ee50ed0c0fc7315bf908fe5506a7 0.003411764716 1122622 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": 680583, "vin": [ { "gen": { "height": 680573 } } ], "vout": [ { "amount": 3411764716, "target": { "key": "bb0c9e7b4e8b41ca1a0ec77fa4b8e13eb188ee50ed0c0fc7315bf908fe5506a7" } } ], "extra": [ 1, 213, 61, 20, 227, 129, 93, 189, 190, 219, 121, 16, 41, 20, 208, 31, 24, 120, 62, 123, 94, 101, 167, 22, 80, 85, 152, 0, 145, 44, 206, 117, 18, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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: