Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15c8060e38b3cb2e0fcdd43b6ae7a3fa6cc695ef8951acb1f1e01b87d25455b9

Tx prefix hash: cd22db83978893fa3eac1765e7d4a3a4190ed3ba0ad4a0b8e938ed8254048ca4
Tx public key: 4fb350325358e0ac24ef4e1bb7025a771cedbf8d48ef876d4ce5f36d5bc0d079
Timestamp: 1732395071 Timestamp [UCT]: 2024-11-23 20:51:11 Age [y:d:h:m:s]: 00:034:13:33:29
Block: 1160211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24740 RingCT/type: yes/0
Extra: 014fb350325358e0ac24ef4e1bb7025a771cedbf8d48ef876d4ce5f36d5bc0d0790211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d6b290773eb2efc1a6e23fd03d0e8a4b51940d01f758daa03544b4ddb82c4c2 0.600000000000 1645854 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": 1160221, "vin": [ { "gen": { "height": 1160211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d6b290773eb2efc1a6e23fd03d0e8a4b51940d01f758daa03544b4ddb82c4c2" } } ], "extra": [ 1, 79, 179, 80, 50, 83, 88, 224, 172, 36, 239, 78, 27, 183, 2, 90, 119, 28, 237, 191, 141, 72, 239, 135, 109, 76, 229, 243, 109, 91, 192, 208, 121, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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