Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c0c4f1edeae1d6e5ca0ad6354fab122a62460f85affbdd881b0ceff07298bce

Tx prefix hash: 8037e0d45e8a20dec2d8ab0a27f2d3612ff5d5b0acf8d3249583f092865b7f8b
Tx public key: 35887a36fd4b655581d26b42402fb40348502735f5233766c9656b4d0c8e6881
Timestamp: 1706335244 Timestamp [UCT]: 2024-01-27 06:00:44 Age [y:d:h:m:s]: 00:333:00:48:03
Block: 944240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238462 RingCT/type: yes/0
Extra: 0135887a36fd4b655581d26b42402fb40348502735f5233766c9656b4d0c8e68810211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0a45d7f69bd4782b16cadd13d8f013a6ec2df1e89f92eb3369d227450f8505f 0.600000000000 1402476 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": 944250, "vin": [ { "gen": { "height": 944240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0a45d7f69bd4782b16cadd13d8f013a6ec2df1e89f92eb3369d227450f8505f" } } ], "extra": [ 1, 53, 136, 122, 54, 253, 75, 101, 85, 129, 210, 107, 66, 64, 47, 180, 3, 72, 80, 39, 53, 245, 35, 55, 102, 201, 101, 107, 77, 12, 142, 104, 129, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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