Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40b4afc8c2ac07b0d62149a1a934844fe89e1a26b405b46d3c48862be73c9b71

Tx prefix hash: 28abb70cd1d42eba131a2fe320e066299988a087095138b2a47d8dccc029efc8
Tx public key: 76e341e8b1d28cad35eaa12424e17cb35d686fba91273d6858cacd5f2d5d9e10
Timestamp: 1702897084 Timestamp [UCT]: 2023-12-18 10:58:04 Age [y:d:h:m:s]: 01:113:10:43:36
Block: 915761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342211 RingCT/type: yes/0
Extra: 0176e341e8b1d28cad35eaa12424e17cb35d686fba91273d6858cacd5f2d5d9e1002110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36dcd71e8daa3be94462bc1777d966ae9d53d474272ec0fad3631d47ac8001fc 0.600000000000 1373185 of 15

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": 915771, "vin": [ { "gen": { "height": 915761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36dcd71e8daa3be94462bc1777d966ae9d53d474272ec0fad3631d47ac8001fc" } } ], "extra": [ 1, 118, 227, 65, 232, 177, 210, 140, 173, 53, 234, 161, 36, 36, 225, 124, 179, 93, 104, 111, 186, 145, 39, 61, 104, 88, 202, 205, 95, 45, 93, 158, 16, 2, 17, 0, 0, 0, 1, 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