Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89cbb73ba1351a847efa0a69c13b0de03872ef250a05d2a36db9f8ca9e35b746

Tx prefix hash: 926192485048de9e97c4f11805e88d417320a77180e9cbf01ee27feb2a350a47
Tx public key: cc763860efcef3534b298a752e7e112e39693a2750aacb40d4abe45d5f525e36
Timestamp: 1731133406 Timestamp [UCT]: 2024-11-09 06:23:26 Age [y:d:h:m:s]: 00:173:15:28:20
Block: 1149775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123938 RingCT/type: yes/0
Extra: 01cc763860efcef3534b298a752e7e112e39693a2750aacb40d4abe45d5f525e36021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d080fb4c2531ce310022bad52b9b6dc5900dfa98bf9fd675e282a39e09bcc3b5 0.600000000000 1634936 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": 1149785, "vin": [ { "gen": { "height": 1149775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d080fb4c2531ce310022bad52b9b6dc5900dfa98bf9fd675e282a39e09bcc3b5" } } ], "extra": [ 1, 204, 118, 56, 96, 239, 206, 243, 83, 75, 41, 138, 117, 46, 126, 17, 46, 57, 105, 58, 39, 80, 170, 203, 64, 212, 171, 228, 93, 95, 82, 94, 54, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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