Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccbe7692cbc43c05af4e0b514cd3d2e39c1e1ef9bb15146d5ba69e5d1e532617

Tx prefix hash: d0076119a94fff9b01d3accd0d51c1bc41ee1706b31783bddb8752e2244548d0
Tx public key: 10bf8141dc95e12ab11d8d8ff420eaec701fd084ee77afa9e3cf2874b814c383
Timestamp: 1704888404 Timestamp [UCT]: 2024-01-10 12:06:44 Age [y:d:h:m:s]: 00:308:21:19:24
Block: 932264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221169 RingCT/type: yes/0
Extra: 0110bf8141dc95e12ab11d8d8ff420eaec701fd084ee77afa9e3cf2874b814c3830211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b5ba6d5cb5d9760b7c7f9b767c31b55600864434d800e246496da9f684ce6a4 0.600000000000 1390194 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": 932274, "vin": [ { "gen": { "height": 932264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b5ba6d5cb5d9760b7c7f9b767c31b55600864434d800e246496da9f684ce6a4" } } ], "extra": [ 1, 16, 191, 129, 65, 220, 149, 225, 42, 177, 29, 141, 143, 244, 32, 234, 236, 112, 31, 208, 132, 238, 119, 175, 169, 227, 207, 40, 116, 184, 20, 195, 131, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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