Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d32c2836bb3c407bf9b9659f2b5c90813f17aea73cb36cbef6b974b8f534981

Tx prefix hash: 216b9addbe243383b43fa7b399165334cb01421c978ad82c8f40047aeb2abfda
Tx public key: 033f22b06408b1d4a795e505f97c179d487bbc60e1c9ed8c2f156264285c84b0
Timestamp: 1711158198 Timestamp [UCT]: 2024-03-23 01:43:18 Age [y:d:h:m:s]: 00:360:08:41:38
Block: 984272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257647 RingCT/type: yes/0
Extra: 01033f22b06408b1d4a795e505f97c179d487bbc60e1c9ed8c2f156264285c84b002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8babcf62fc7bb57401953debf3330d4f9d89c4d8e16b808ef2651774c9d89d0 0.600000000000 1444441 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": 984282, "vin": [ { "gen": { "height": 984272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8babcf62fc7bb57401953debf3330d4f9d89c4d8e16b808ef2651774c9d89d0" } } ], "extra": [ 1, 3, 63, 34, 176, 100, 8, 177, 212, 167, 149, 229, 5, 249, 124, 23, 157, 72, 123, 188, 96, 225, 201, 237, 140, 47, 21, 98, 100, 40, 92, 132, 176, 2, 17, 0, 0, 0, 1, 82, 212, 126, 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