Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87277eda7e9650f9f72502f3de7821b6fbe8a39935b7e70a2cdbdada7a2191a8

Tx prefix hash: 4f6cd05118ee662fbd9c030ba1ec2c45a3e9f193be45d8fc0198604a63eef191
Tx public key: cfacfc5ffca89311118d823a0c7d702d1c9cee7db942ee8d91ca79d5ca07e36e
Timestamp: 1727238484 Timestamp [UCT]: 2024-09-25 04:28:04 Age [y:d:h:m:s]: 01:047:00:54:55
Block: 1117560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292016 RingCT/type: yes/0
Extra: 01cfacfc5ffca89311118d823a0c7d702d1c9cee7db942ee8d91ca79d5ca07e36e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91de73596f6fc1411d40e9e1f487d8c38902626d3575139430b32630edef4f2e 0.600000000000 1598445 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": 1117570, "vin": [ { "gen": { "height": 1117560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91de73596f6fc1411d40e9e1f487d8c38902626d3575139430b32630edef4f2e" } } ], "extra": [ 1, 207, 172, 252, 95, 252, 168, 147, 17, 17, 141, 130, 58, 12, 125, 112, 45, 28, 156, 238, 125, 185, 66, 238, 141, 145, 202, 121, 213, 202, 7, 227, 110, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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