Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7456c489e4daf8943d4cf3a292d737d635247760109712803594f9ebda3396a

Tx prefix hash: fc41dda2d2a5c162474bd2270556b82d330cc60806b1c4c92badc89b22e89ad6
Tx public key: a28c68a7fef38e0ef17409ed937802d6d798c1b31dd0d6e38b9b49fe332bbd1c
Timestamp: 1698529864 Timestamp [UCT]: 2023-10-28 21:51:04 Age [y:d:h:m:s]: 01:216:23:38:43
Block: 879774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416110 RingCT/type: yes/0
Extra: 01a28c68a7fef38e0ef17409ed937802d6d798c1b31dd0d6e38b9b49fe332bbd1c02110000001c33af99f4000000000000000000

1 output(s) for total of 0.746351722000 dcy

stealth address amount amount idx
00: 176c6ab93c3df3192ac67a15fefccd27f8885bce8f4de624056c7467ffe958f4 0.746351722000 1335312 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": 879784, "vin": [ { "gen": { "height": 879774 } } ], "vout": [ { "amount": 746351722, "target": { "key": "176c6ab93c3df3192ac67a15fefccd27f8885bce8f4de624056c7467ffe958f4" } } ], "extra": [ 1, 162, 140, 104, 167, 254, 243, 142, 14, 241, 116, 9, 237, 147, 120, 2, 214, 215, 152, 193, 179, 29, 208, 214, 227, 139, 155, 73, 254, 51, 43, 189, 28, 2, 17, 0, 0, 0, 28, 51, 175, 153, 244, 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