Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2950f3ba2f23a1b65a6bc8eda939c14f4be851a855a6761be28b5d296b54e981

Tx prefix hash: 2a7fae94caa0e830e2cf8cd8e4ae9b77baa0dc11979825fd7dc209741c7cb873
Tx public key: 219e5b05f773ac52c4c640df978cacc66258821fb9d159d97c02e02b78dcbd27
Timestamp: 1649768837 Timestamp [UTC]: 2022-04-12 13:07:17 Age [y:d:h:m:s]: 04:224:16:15:25
Block: 478635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1204859 RingCT/type: yes/0
Extra: 01219e5b05f773ac52c4c640df978cacc66258821fb9d159d97c02e02b78dcbd2702110000002a5eb576c5000000000000000000

1 output(s) for total of 0.015927459508 xmr

stealth address amount amount idx tag
00: 1cf5c3d807eeea0e9022679a2ee21378971cba48327bccda65b2fd893499cc54 0.015927459508 899416 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": 478645, "vin": [ { "gen": { "height": 478635 } } ], "vout": [ { "amount": 15927459508, "target": { "key": "1cf5c3d807eeea0e9022679a2ee21378971cba48327bccda65b2fd893499cc54" } } ], "extra": [ 1, 33, 158, 91, 5, 247, 115, 172, 82, 196, 198, 64, 223, 151, 140, 172, 198, 98, 88, 130, 31, 185, 209, 89, 217, 124, 2, 224, 43, 120, 220, 189, 39, 2, 17, 0, 0, 0, 42, 94, 181, 118, 197, 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: