Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a49510e5b6af61157d21af7ba0a99aa9b81efa3de4c9a5c82c86138d3f597a5

Tx prefix hash: 583ec88eff2ff24819cd0aa305e2080f2eacd59aebd2bfef0c7ad71055f13067
Tx public key: c90244b3912304b62ec0d0a2cc8e45ed33057780b3ec171b4f26e780e4b72f6b
Timestamp: 1701087630 Timestamp [UCT]: 2023-11-27 12:20:30 Age [y:d:h:m:s]: 01:151:01:33:15
Block: 900759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369149 RingCT/type: yes/0
Extra: 01c90244b3912304b62ec0d0a2cc8e45ed33057780b3ec171b4f26e780e4b72f6b02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.635933191000 dcy

stealth address amount amount idx
00: a77542f4628a4c43bb3f40a7ea8c51cdd6d8a00e710721a6dc436c98da6dc9c4 0.635933191000 1357278 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": 900769, "vin": [ { "gen": { "height": 900759 } } ], "vout": [ { "amount": 635933191, "target": { "key": "a77542f4628a4c43bb3f40a7ea8c51cdd6d8a00e710721a6dc436c98da6dc9c4" } } ], "extra": [ 1, 201, 2, 68, 179, 145, 35, 4, 182, 46, 192, 208, 162, 204, 142, 69, 237, 51, 5, 119, 128, 179, 236, 23, 27, 79, 38, 231, 128, 228, 183, 47, 107, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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