Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 291ba6b3dfa78ce868b38cf80d65b9e8b825f4438d8fec2ee1783ab2238104e4

Tx prefix hash: cd7b716fb5495bae7e2f73bef9bc8a0e75d218d33bbac0cda8e08fcae327cc62
Tx public key: 2cbd5a960379a5e06dcc376d529cc665282b5f086300e7b293e561dea831f855
Timestamp: 1697471286 Timestamp [UCT]: 2023-10-16 15:48:06 Age [y:d:h:m:s]: 01:161:20:26:30
Block: 870976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376693 RingCT/type: yes/0
Extra: 012cbd5a960379a5e06dcc376d529cc665282b5f086300e7b293e561dea831f85502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.798169225000 dcy

stealth address amount amount idx
00: 2534d4f6a54028a383bd2cbc45e741f1b166622283148ea1c9e3b30213ec2eb0 0.798169225000 1325943 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": 870986, "vin": [ { "gen": { "height": 870976 } } ], "vout": [ { "amount": 798169225, "target": { "key": "2534d4f6a54028a383bd2cbc45e741f1b166622283148ea1c9e3b30213ec2eb0" } } ], "extra": [ 1, 44, 189, 90, 150, 3, 121, 165, 224, 109, 204, 55, 109, 82, 156, 198, 101, 40, 43, 95, 8, 99, 0, 231, 178, 147, 229, 97, 222, 168, 49, 248, 85, 2, 17, 0, 0, 0, 5, 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