Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0bcfeda3e448e014c8845e7f4fd46f9ea39f9c0b9027de9267f126ac7c9517

Tx prefix hash: bc2c63924877e4a6c4f7701547768f0254771c8fc91fb9ae1316f9c13648e13b
Tx public key: 5755ef78164abdb3d25cd462c082aa09617d0ce7cac5487bea216e49910c188c
Timestamp: 1579202797 Timestamp [UTC]: 2020-01-16 19:26:37 Age [y:d:h:m:s]: 06:310:04:23:07
Block: 47047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1635969 RingCT/type: yes/0
Extra: 015755ef78164abdb3d25cd462c082aa09617d0ce7cac5487bea216e49910c188c021100000073bd0f9f9f000000000000000000

1 output(s) for total of 0.428661615316 xmr

stealth address amount amount idx tag
00: 4207194b4191de357a66156d446c1d9bda66ee047110a831d80e61d82696a0e8 0.428661615316 86863 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": 47057, "vin": [ { "gen": { "height": 47047 } } ], "vout": [ { "amount": 428661615316, "target": { "key": "4207194b4191de357a66156d446c1d9bda66ee047110a831d80e61d82696a0e8" } } ], "extra": [ 1, 87, 85, 239, 120, 22, 74, 189, 179, 210, 92, 212, 98, 192, 130, 170, 9, 97, 125, 12, 231, 202, 197, 72, 123, 234, 33, 110, 73, 145, 12, 24, 140, 2, 17, 0, 0, 0, 115, 189, 15, 159, 159, 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: