Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d07475d8124f14d552a563f48d6e387b5cfcb7693d8ca81c0afc255e47ce07ba

Tx prefix hash: d3d958eb6f9da9069184de056fb0b834f03c85eb532cd4d221558ace06a9bed3
Tx public key: b3042307147c332f1aa8d3ca65e1506430aea974ad4760203e03e46cc317af17
Timestamp: 1681963105 Timestamp [UCT]: 2023-04-20 03:58:25 Age [y:d:h:m:s]: 02:059:22:00:19
Block: 742456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564881 RingCT/type: yes/0
Extra: 01b3042307147c332f1aa8d3ca65e1506430aea974ad4760203e03e46cc317af1702110000000175e3f0e9000000000000000000

1 output(s) for total of 2.127821918000 dcy

stealth address amount amount idx
00: 2cb03e981c8dbd1a92b8920a9f82a82c7a75e7b294ed4c7fce537bcc9ef4cc34 2.127821918000 1189427 of 0

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": 742466, "vin": [ { "gen": { "height": 742456 } } ], "vout": [ { "amount": 2127821918, "target": { "key": "2cb03e981c8dbd1a92b8920a9f82a82c7a75e7b294ed4c7fce537bcc9ef4cc34" } } ], "extra": [ 1, 179, 4, 35, 7, 20, 124, 51, 47, 26, 168, 211, 202, 101, 225, 80, 100, 48, 174, 169, 116, 173, 71, 96, 32, 62, 3, 228, 108, 195, 23, 175, 23, 2, 17, 0, 0, 0, 1, 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