Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3915b2b8a2f468f451cacb054b67bb7b46aa378c7818707ec5c5bd86ac2e5ecf

Tx prefix hash: f79c1db85538ccfec309a1217be12dd03c4fc9b3cefc32fae4d46f11b74b28e5
Tx public key: a7f885c1ce4c5612a474c294048ac789f5381b02bbef865ecc22dfb25c45596e
Timestamp: 1720284477 Timestamp [UCT]: 2024-07-06 16:47:57 Age [y:d:h:m:s]: 00:275:07:32:36
Block: 1059908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196699 RingCT/type: yes/0
Extra: 01a7f885c1ce4c5612a474c294048ac789f5381b02bbef865ecc22dfb25c45596e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c9d6c36c9838fefb459e338a3538a4df5f84feb9e3c94759e7ac7d2044f558b 0.600000000000 1530379 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": 1059918, "vin": [ { "gen": { "height": 1059908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c9d6c36c9838fefb459e338a3538a4df5f84feb9e3c94759e7ac7d2044f558b" } } ], "extra": [ 1, 167, 248, 133, 193, 206, 76, 86, 18, 164, 116, 194, 148, 4, 138, 199, 137, 245, 56, 27, 2, 187, 239, 134, 94, 204, 34, 223, 178, 92, 69, 89, 110, 2, 17, 0, 0, 0, 1, 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