Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5d9baeba6dddb9ffc4d2602d9440bb87391f6ed47f1be866a3302e0f7369ea

Tx prefix hash: ab4aabeb2c0775f46c18bdc54e64d053e8778bc3629d1aeb93c394094d4b81a8
Tx public key: 610a60d26291c98722fb70db554d8ae81d4badecdeaee75913d5f60b014f5056
Timestamp: 1677430977 Timestamp [UCT]: 2023-02-26 17:02:57 Age [y:d:h:m:s]: 02:051:01:44:04
Block: 705516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558077 RingCT/type: yes/0
Extra: 01610a60d26291c98722fb70db554d8ae81d4badecdeaee75913d5f60b014f505602110000000183600029000000000000000000

1 output(s) for total of 2.820541691000 dcy

stealth address amount amount idx
00: b728ad5808144ba17eb1709a6ab8f600e054eef9e40a9bde5827700ae70fe8a6 2.820541691000 1149219 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": 705526, "vin": [ { "gen": { "height": 705516 } } ], "vout": [ { "amount": 2820541691, "target": { "key": "b728ad5808144ba17eb1709a6ab8f600e054eef9e40a9bde5827700ae70fe8a6" } } ], "extra": [ 1, 97, 10, 96, 210, 98, 145, 201, 135, 34, 251, 112, 219, 85, 77, 138, 232, 29, 75, 173, 236, 222, 174, 231, 89, 19, 213, 246, 11, 1, 79, 80, 86, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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