Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f67a55ab61c58cf8bd1d64fe65ed81585192a6b49f5576624e45d7f96fe4ce

Tx prefix hash: a1fed086f67caaaeba8c2407609fb9af74c618b97cfcfc1c6eb589d4288a052b
Tx public key: 0b466cdb0feaa7d89b5cbb34ceb15c50748fd04e593aba719d6c3b44cd95bd96
Timestamp: 1713253751 Timestamp [UCT]: 2024-04-16 07:49:11 Age [y:d:h:m:s]: 00:358:15:28:29
Block: 1001605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256411 RingCT/type: yes/0
Extra: 010b466cdb0feaa7d89b5cbb34ceb15c50748fd04e593aba719d6c3b44cd95bd9602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41d7c1fe13e3ca021281ad6ef420ff6cc467a7e1d0230053bc1518b43bffcf7f 0.600000000000 1462111 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": 1001615, "vin": [ { "gen": { "height": 1001605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41d7c1fe13e3ca021281ad6ef420ff6cc467a7e1d0230053bc1518b43bffcf7f" } } ], "extra": [ 1, 11, 70, 108, 219, 15, 234, 167, 216, 155, 92, 187, 52, 206, 177, 92, 80, 116, 143, 208, 78, 89, 58, 186, 113, 157, 108, 59, 68, 205, 149, 189, 150, 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