Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 451c722f9ce70ca5b5f734c95bbe84c2cd18be7630dfed2db4e3b56fb87f384c

Tx prefix hash: 0b7403d9aa15377b889aa485f93048100afd3ab38b4e6617b8d504e1594c21ea
Tx public key: b3dc78a89a9cd3160e128fa92daf51f02aaf47b7818fc82e3d58553c6746b975
Timestamp: 1714055054 Timestamp [UCT]: 2024-04-25 14:24:14 Age [y:d:h:m:s]: 01:025:09:55:55
Block: 1008265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279128 RingCT/type: yes/0
Extra: 01b3dc78a89a9cd3160e128fa92daf51f02aaf47b7818fc82e3d58553c6746b97502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc6d083ccd9aca367c522a6e7c0d8c79ad21075c5b348a7d0175eea0a73a2821 0.600000000000 1469733 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": 1008275, "vin": [ { "gen": { "height": 1008265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc6d083ccd9aca367c522a6e7c0d8c79ad21075c5b348a7d0175eea0a73a2821" } } ], "extra": [ 1, 179, 220, 120, 168, 154, 156, 211, 22, 14, 18, 143, 169, 45, 175, 81, 240, 42, 175, 71, 183, 129, 143, 200, 46, 61, 88, 85, 60, 103, 70, 185, 117, 2, 17, 0, 0, 0, 5, 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