Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb617efc612f19839caa2de289df16c7776cf37cc9bf1b4f65747a358282da55

Tx prefix hash: ae4349973afd8b0e6d2859a9216c8ef15eb526f0661781946830f7d2a11375f4
Tx public key: 542a1ff9a19104d2609c46f86ca41617f8ad8bc233fc7fb043ab14f15b9e71f7
Timestamp: 1630057554 Timestamp [UTC]: 2021-08-27 09:45:54 Age [y:d:h:m:s]: 05:084:16:49:29
Block: 321739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359831 RingCT/type: yes/0
Extra: 01542a1ff9a19104d2609c46f86ca41617f8ad8bc233fc7fb043ab14f15b9e71f702110000000fdeae9d30000000000000000000

1 output(s) for total of 0.052716381401 xmr

stealth address amount amount idx tag
00: e41e461bdbe749eabfcb221fafcaee074faf72d9d0ebe2ae93d5e189f6e98d2a 0.052716381401 667798 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": 321749, "vin": [ { "gen": { "height": 321739 } } ], "vout": [ { "amount": 52716381401, "target": { "key": "e41e461bdbe749eabfcb221fafcaee074faf72d9d0ebe2ae93d5e189f6e98d2a" } } ], "extra": [ 1, 84, 42, 31, 249, 161, 145, 4, 210, 96, 156, 70, 248, 108, 164, 22, 23, 248, 173, 139, 194, 51, 252, 127, 176, 67, 171, 20, 241, 91, 158, 113, 247, 2, 17, 0, 0, 0, 15, 222, 174, 157, 48, 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: