Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b23ba3ea84783a8e3569f2da61684eab93205c97e3681f26a0deb50c98b85601

Tx prefix hash: 9841fc8cea0e3d8153a09d8fef05ceb929be4c0f62a92e020f73c7b4b3031369
Tx public key: 6a75981449c710f02953f6d9c4b8535ad8a45a305ddb8ac730c051216f06fc6b
Timestamp: 1634573383 Timestamp [UCT]: 2021-10-18 16:09:43 Age [y:d:h:m:s]: 03:045:16:35:58
Block: 355641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 810663 RingCT/type: yes/0
Extra: 016a75981449c710f02953f6d9c4b8535ad8a45a305ddb8ac730c051216f06fc6b021100000008fdc024ec000000000000000000

1 output(s) for total of 40.704829934000 dcy

stealth address amount amount idx
00: 3c45f74e0faed0f5ee75c664d9c9c4be44a4ea59c3ae50ca186c06da1c397252 40.704829934000 725979 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": 355651, "vin": [ { "gen": { "height": 355641 } } ], "vout": [ { "amount": 40704829934, "target": { "key": "3c45f74e0faed0f5ee75c664d9c9c4be44a4ea59c3ae50ca186c06da1c397252" } } ], "extra": [ 1, 106, 117, 152, 20, 73, 199, 16, 240, 41, 83, 246, 217, 196, 184, 83, 90, 216, 164, 90, 48, 93, 219, 138, 199, 48, 192, 81, 33, 111, 6, 252, 107, 2, 17, 0, 0, 0, 8, 253, 192, 36, 236, 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