Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a59ae9ae444520ef473dcdd5160acbf2bb3745b39394bc72f15b228a9c275b97

Tx prefix hash: 7d3393105e1d4abcacfb2b999820e878aacd637a6beb396ecc1f6f4abae1e35c
Tx public key: af80212f9b9c608e7f7ee90efb048ca7d2884ea8970e7905cfa13c588e63df8a
Timestamp: 1632258140 Timestamp [UCT]: 2021-09-21 21:02:20 Age [y:d:h:m:s]: 03:046:00:16:20
Block: 338348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 808989 RingCT/type: yes/0
Extra: 01af80212f9b9c608e7f7ee90efb048ca7d2884ea8970e7905cfa13c588e63df8a02110000000206faf294000000000000000000

1 output(s) for total of 46.442229005000 dcy

stealth address amount amount idx
00: 0b65ffc54b9871e0f934da02ccc5ddbf5a0d0cd192d0e8fb2278d59df20ab8f8 46.442229005000 696373 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 dinasty-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": 338358, "vin": [ { "gen": { "height": 338348 } } ], "vout": [ { "amount": 46442229005, "target": { "key": "0b65ffc54b9871e0f934da02ccc5ddbf5a0d0cd192d0e8fb2278d59df20ab8f8" } } ], "extra": [ 1, 175, 128, 33, 47, 155, 156, 96, 142, 127, 126, 233, 14, 251, 4, 140, 167, 210, 136, 78, 168, 151, 14, 121, 5, 207, 161, 60, 88, 142, 99, 223, 138, 2, 17, 0, 0, 0, 2, 6, 250, 242, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8