Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2936cf27ebaeaf01ebdd185e980b7514fd29e79f4de5bc4f01e817b8368fe853

Tx prefix hash: 435eced98e1c8ee4b562a130f1188733b4702f6b4ecff3f79bab02b15ba35d71
Tx public key: d4c6a1e9f3f7dd87a44f94c2de562e24f61c722fb91701e8611a3969b768d47c
Timestamp: 1673700831 Timestamp [UCT]: 2023-01-14 12:53:51 Age [y:d:h:m:s]: 02:007:11:51:49
Block: 674575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527218 RingCT/type: yes/0
Extra: 01d4c6a1e9f3f7dd87a44f94c2de562e24f61c722fb91701e8611a3969b768d47c021100000004272bcc39000000000000000000

1 output(s) for total of 3.571518846000 dcy

stealth address amount amount idx
00: 9c8abead10f4dd0d016abb6fcbd8b9c9529b56b8a0eabf0d2f2d7f19cb5b04c4 3.571518846000 1116228 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": 674585, "vin": [ { "gen": { "height": 674575 } } ], "vout": [ { "amount": 3571518846, "target": { "key": "9c8abead10f4dd0d016abb6fcbd8b9c9529b56b8a0eabf0d2f2d7f19cb5b04c4" } } ], "extra": [ 1, 212, 198, 161, 233, 243, 247, 221, 135, 164, 79, 148, 194, 222, 86, 46, 36, 246, 28, 114, 47, 185, 23, 1, 232, 97, 26, 57, 105, 183, 104, 212, 124, 2, 17, 0, 0, 0, 4, 39, 43, 204, 57, 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