Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa0c6a2eadcfb39294b95fd1aa80d22548a8fd4b000ccad23399d171b43de4f2

Tx prefix hash: 2ee8a25a44ac4a18dd4784c3c3c3449a834c4fc0d4e606422b6cb2146d39011e
Tx public key: 3b1f69fde5bb269938552a30c7f530a7219993fa675324d6e772ab69022e551b
Timestamp: 1617471684 Timestamp [UTC]: 2021-04-03 17:41:24 Age [y:d:h:m:s]: 05:038:03:52:34
Block: 232557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1298808 RingCT/type: yes/0
Extra: 013b1f69fde5bb269938552a30c7f530a7219993fa675324d6e772ab69022e551b021100000047ece3035d000000000000000000

1 output(s) for total of 0.104098074836 xmr

stealth address amount amount idx tag
00: f08730f4b3519128d65018c660a00ea55b474569c8e4371a6d7a145f1d5e9e02 0.104098074836 483161 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": 232567, "vin": [ { "gen": { "height": 232557 } } ], "vout": [ { "amount": 104098074836, "target": { "key": "f08730f4b3519128d65018c660a00ea55b474569c8e4371a6d7a145f1d5e9e02" } } ], "extra": [ 1, 59, 31, 105, 253, 229, 187, 38, 153, 56, 85, 42, 48, 199, 245, 48, 167, 33, 153, 147, 250, 103, 83, 36, 214, 231, 114, 171, 105, 2, 46, 85, 27, 2, 17, 0, 0, 0, 71, 236, 227, 3, 93, 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: