Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cdb123d337a90206013e2a63d23e8a3d3dfb0e80c3bbc2ec9c70348c80e7b41

Tx prefix hash: b617a7c96c61d5fa729ee36ac0b5c67ea3be80cfecf5ba84306a9b133a6e3e67
Tx public key: a07d1ee3aa5a70e554d4b21fb70edb284e49a6f8191931a7c6e567a22fd85826
Timestamp: 1705555925 Timestamp [UCT]: 2024-01-18 05:32:05 Age [y:d:h:m:s]: 01:042:03:29:14
Block: 937777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291192 RingCT/type: yes/0
Extra: 01a07d1ee3aa5a70e554d4b21fb70edb284e49a6f8191931a7c6e567a22fd8582602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b8d62f11a060a9d621a6dce1c47139e291fc00fc6fbb80d75eed0de2810af20 0.600000000000 1395841 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": 937787, "vin": [ { "gen": { "height": 937777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b8d62f11a060a9d621a6dce1c47139e291fc00fc6fbb80d75eed0de2810af20" } } ], "extra": [ 1, 160, 125, 30, 227, 170, 90, 112, 229, 84, 212, 178, 31, 183, 14, 219, 40, 78, 73, 166, 248, 25, 25, 49, 167, 198, 229, 103, 162, 47, 216, 88, 38, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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