Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c60eba623af2d4c885bc5eee20a494fec7cd5ba4b6ed79dc22e9922e13b3ded

Tx prefix hash: 0727df9aa6400706ea42b39d313cae85f8fd3f9df10c584f2b25e05935d722f3
Tx public key: 8d6ac3f217e13c58ec9b72b1c4aebb4389d8e63555c992610cbea4e521bdd5f3
Timestamp: 1682794478 Timestamp [UCT]: 2023-04-29 18:54:38 Age [y:d:h:m:s]: 01:339:13:42:40
Block: 749350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503938 RingCT/type: yes/0
Extra: 018d6ac3f217e13c58ec9b72b1c4aebb4389d8e63555c992610cbea4e521bdd5f3021100000003b3164c24000000000000000000

1 output(s) for total of 2.018796691000 dcy

stealth address amount amount idx
00: 9b926107c4dd6b40491c24b5338656fec21f08397ddd04ff09c21f535bed7b86 2.018796691000 1197305 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": 749360, "vin": [ { "gen": { "height": 749350 } } ], "vout": [ { "amount": 2018796691, "target": { "key": "9b926107c4dd6b40491c24b5338656fec21f08397ddd04ff09c21f535bed7b86" } } ], "extra": [ 1, 141, 106, 195, 242, 23, 225, 60, 88, 236, 155, 114, 177, 196, 174, 187, 67, 137, 216, 230, 53, 85, 201, 146, 97, 12, 190, 164, 229, 33, 189, 213, 243, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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