Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17ecfea0c2acaaff3b409848ac1345ef6d3b7d292564bc8f0e2747377b37081d

Tx prefix hash: 8d2c2764ea35f845eeb5b55dea4086016a6fd238f2963089d5a5d9b62afe53ce
Tx public key: 795d27079c5600fd1f43ded96854b31a8306db9c907b14979eb28697ba468d14
Timestamp: 1702631626 Timestamp [UCT]: 2023-12-15 09:13:46 Age [y:d:h:m:s]: 01:181:19:06:50
Block: 913558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391033 RingCT/type: yes/0
Extra: 01795d27079c5600fd1f43ded96854b31a8306db9c907b14979eb28697ba468d1402110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e21b5f2f1b674dfbb267813e0a6d324f776c943f7c6a503f0527c126acf2761 0.600000000000 1370832 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": 913568, "vin": [ { "gen": { "height": 913558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e21b5f2f1b674dfbb267813e0a6d324f776c943f7c6a503f0527c126acf2761" } } ], "extra": [ 1, 121, 93, 39, 7, 156, 86, 0, 253, 31, 67, 222, 217, 104, 84, 179, 26, 131, 6, 219, 156, 144, 123, 20, 151, 158, 178, 134, 151, 186, 70, 141, 20, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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