Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 425753c3071ca66a3f3b7133de2061d634e341f375dbaf887f26363e0f8268d5

Tx prefix hash: c88992099d65a945b1dad7347f2c0a6c59c0bba92577610ad564988396b6f33e
Tx public key: 1c4b9e9e51a62b0b111c3e6ba605c6c55b6b9d3425cca737b304e76580a5aaa1
Timestamp: 1715465486 Timestamp [UCT]: 2024-05-11 22:11:26 Age [y:d:h:m:s]: 00:186:20:14:50
Block: 1019987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133717 RingCT/type: yes/0
Extra: 011c4b9e9e51a62b0b111c3e6ba605c6c55b6b9d3425cca737b304e76580a5aaa102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89dd949cd13dc314df339b46f8ea90319671e8b426c9af9462399d023ccd6744 0.600000000000 1484046 of 15

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": 1019997, "vin": [ { "gen": { "height": 1019987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89dd949cd13dc314df339b46f8ea90319671e8b426c9af9462399d023ccd6744" } } ], "extra": [ 1, 28, 75, 158, 158, 81, 166, 43, 11, 17, 28, 62, 107, 166, 5, 198, 197, 91, 107, 157, 52, 37, 204, 167, 55, 179, 4, 231, 101, 128, 165, 170, 161, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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