Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b73ef528e09244eed7db061f441c177ca6667d5a51ed610065fb9b2246f0f006

Tx prefix hash: 362b4c03bb7b5a697aea0b9bf9070bac2e952f25a89d44e59b52e198bb2e3c3c
Tx public key: e52eb1d86a93aa518b82234ef5600b11b41479077b913a98ac9b1d1aeb9b9064
Timestamp: 1639154167 Timestamp [UCT]: 2021-12-10 16:36:07 Age [y:d:h:m:s]: 03:325:19:31:22
Block: 392609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1009307 RingCT/type: yes/0
Extra: 01e52eb1d86a93aa518b82234ef5600b11b41479077b913a98ac9b1d1aeb9b9064021100000002c99b772e000000000000000000

1 output(s) for total of 30.698967248000 dcy

stealth address amount amount idx
00: 8ce522cb6e54aba94b785b04f1d4dab5d731a008807b124578a2b3302712fad2 30.698967248000 789544 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": 392619, "vin": [ { "gen": { "height": 392609 } } ], "vout": [ { "amount": 30698967248, "target": { "key": "8ce522cb6e54aba94b785b04f1d4dab5d731a008807b124578a2b3302712fad2" } } ], "extra": [ 1, 229, 46, 177, 216, 106, 147, 170, 81, 139, 130, 35, 78, 245, 96, 11, 17, 180, 20, 121, 7, 123, 145, 58, 152, 172, 155, 29, 26, 235, 155, 144, 100, 2, 17, 0, 0, 0, 2, 201, 155, 119, 46, 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