Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05134312ca5171f08a5055a4665c7eecb417e2f623f6ba59f0d910676488c6e8

Tx prefix hash: f7de4f8e79eee4d13e3bcd62c02b8d50c3243c2dd079a3f01049f044545c764b
Tx public key: 089cc18c95e848098c93fcbc8351d7a14f595cc67cd5a548cc670243e35d5ded
Timestamp: 1634709531 Timestamp [UCT]: 2021-10-20 05:58:51 Age [y:d:h:m:s]: 03:190:07:01:34
Block: 356652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 913950 RingCT/type: yes/0
Extra: 01089cc18c95e848098c93fcbc8351d7a14f595cc67cd5a548cc670243e35d5ded02110000000dfdc024ec000000000000000000

1 output(s) for total of 40.389110115000 dcy

stealth address amount amount idx
00: be1222b71fba45b0cc8a5c7dd24ae449afbc464f818c434534c382179126a439 40.389110115000 727594 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": 356662, "vin": [ { "gen": { "height": 356652 } } ], "vout": [ { "amount": 40389110115, "target": { "key": "be1222b71fba45b0cc8a5c7dd24ae449afbc464f818c434534c382179126a439" } } ], "extra": [ 1, 8, 156, 193, 140, 149, 232, 72, 9, 140, 147, 252, 188, 131, 81, 215, 161, 79, 89, 92, 198, 124, 213, 165, 72, 204, 103, 2, 67, 227, 93, 93, 237, 2, 17, 0, 0, 0, 13, 253, 192, 36, 236, 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