Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e56709ac9ea5e689b78b93481eb718fae015840ba765270d2a25a28d431ca197

Tx prefix hash: a12d1a0ce0b28c5d16d35bea21ff844da598bbf4d9df1432442e8a97c2319501
Tx public key: 58b9cdd9aecf56a110066fd8b9139c3344db613e8ed075355a710db27676f46c
Timestamp: 1644686141 Timestamp [UTC]: 2022-02-12 17:15:41 Age [y:d:h:m:s]: 04:282:07:43:42
Block: 437151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1245907 RingCT/type: yes/0
Extra: 0158b9cdd9aecf56a110066fd8b9139c3344db613e8ed075355a710db27676f46c02110000000fbf7ee4e7000000000000000000

1 output(s) for total of 0.021854333419 xmr

stealth address amount amount idx tag
00: de921b8a5bb303b5a804e18e0e10f07c8758606d7aa386fa314ffa46ab1127f1 0.021854333419 848702 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": 437161, "vin": [ { "gen": { "height": 437151 } } ], "vout": [ { "amount": 21854333419, "target": { "key": "de921b8a5bb303b5a804e18e0e10f07c8758606d7aa386fa314ffa46ab1127f1" } } ], "extra": [ 1, 88, 185, 205, 217, 174, 207, 86, 161, 16, 6, 111, 216, 185, 19, 156, 51, 68, 219, 97, 62, 142, 208, 117, 53, 90, 113, 13, 178, 118, 118, 244, 108, 2, 17, 0, 0, 0, 15, 191, 126, 228, 231, 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: