Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13645824a64c2a4f38c08fad9255bdf8c18cda3d0a91e29b9c6c368ec0d7d97f

Tx prefix hash: 488dfde96c3dbf7354287e0afee5e2c5c71342695bcbf5068bf2f4e38e4b40ce
Tx public key: e906f7df8d1c13ace122bb6066e73415823fc04b13f850abe4013e8a2ec58e9b
Timestamp: 1609070887 Timestamp [UTC]: 2020-12-27 12:08:07 Age [y:d:h:m:s]: 05:329:12:56:32
Block: 170328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1512733 RingCT/type: yes/0
Extra: 01e906f7df8d1c13ace122bb6066e73415823fc04b13f850abe4013e8a2ec58e9b021100000066c6b81c9d000000000000000000

1 output(s) for total of 0.167352920151 xmr

stealth address amount amount idx tag
00: 236f6b00bc139fc44df5e2be6a0b3455484a6960bad203d5b05dec585b4071f9 0.167352920151 319267 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": 170338, "vin": [ { "gen": { "height": 170328 } } ], "vout": [ { "amount": 167352920151, "target": { "key": "236f6b00bc139fc44df5e2be6a0b3455484a6960bad203d5b05dec585b4071f9" } } ], "extra": [ 1, 233, 6, 247, 223, 141, 28, 19, 172, 225, 34, 187, 96, 102, 231, 52, 21, 130, 63, 192, 75, 19, 248, 80, 171, 228, 1, 62, 138, 46, 197, 142, 155, 2, 17, 0, 0, 0, 102, 198, 184, 28, 157, 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: