Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c153589d409887c92d6292200d4cee457d01af2976176d439d2374b2ce7a8374

Tx prefix hash: 03b860c7adb6d9b3f0bb54abd1d66235272a55b2601998b3dc8b05cd449576c3
Tx public key: 5ddb60f472dfd46b8c213036fdd3af35b82e1bd4489643f360b0550a2a8989dc
Timestamp: 1671353371 Timestamp [UCT]: 2022-12-18 08:49:31 Age [y:d:h:m:s]: 02:028:14:23:25
Block: 655141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542348 RingCT/type: yes/0
Extra: 015ddb60f472dfd46b8c213036fdd3af35b82e1bd4489643f360b0550a2a8989dc021100000001e6d27f9c000000000000000000

1 output(s) for total of 4.142341349000 dcy

stealth address amount amount idx
00: 03f174ceee3d67760173b5f8fa1bef454589aba0d88aee11a96001e64ed0f8bb 4.142341349000 1095686 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": 655151, "vin": [ { "gen": { "height": 655141 } } ], "vout": [ { "amount": 4142341349, "target": { "key": "03f174ceee3d67760173b5f8fa1bef454589aba0d88aee11a96001e64ed0f8bb" } } ], "extra": [ 1, 93, 219, 96, 244, 114, 223, 212, 107, 140, 33, 48, 54, 253, 211, 175, 53, 184, 46, 27, 212, 72, 150, 67, 243, 96, 176, 85, 10, 42, 137, 137, 220, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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