Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 090fb69e4ceee3996a2532ee557d5d117d3f6a6b063c8dc56675e562bcb255dc

Tx prefix hash: 016a57f7379e52e6f162d7469eae9d939ecfba356ed41f858acc297a48898bd8
Tx public key: 99dc1015830b22d9163baf86d1329bd819350d436d070314fee274f6555164a8
Timestamp: 1699716569 Timestamp [UCT]: 2023-11-11 15:29:29 Age [y:d:h:m:s]: 02:076:06:19:42
Block: 889400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574195 RingCT/type: yes/0
Extra: 0199dc1015830b22d9163baf86d1329bd819350d436d070314fee274f6555164a802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.693503395000 dcy

stealth address amount amount idx
00: adf82c771e09b997d9fbfed8c5db9dbf369d70de9cc44b9c5ee42d4eac58334f 0.693503395000 1345397 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": 889410, "vin": [ { "gen": { "height": 889400 } } ], "vout": [ { "amount": 693503395, "target": { "key": "adf82c771e09b997d9fbfed8c5db9dbf369d70de9cc44b9c5ee42d4eac58334f" } } ], "extra": [ 1, 153, 220, 16, 21, 131, 11, 34, 217, 22, 59, 175, 134, 209, 50, 155, 216, 25, 53, 13, 67, 109, 7, 3, 20, 254, 226, 116, 246, 85, 81, 100, 168, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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