Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 932bfc6ea67d68b176dfd80028f8ba6ce732c15a085577829ece7c9fb380f739

Tx prefix hash: 6f51c727a315a7bb79118cc96b21bf135331b992fd0e99edbed421e78eec2a92
Tx public key: 813a6e70039c1901dba2a06d3d574356013fd2632f6c91c0a839997c244de2ce
Timestamp: 1705307802 Timestamp [UCT]: 2024-01-15 08:36:42 Age [y:d:h:m:s]: 01:118:10:55:51
Block: 935730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345787 RingCT/type: yes/0
Extra: 01813a6e70039c1901dba2a06d3d574356013fd2632f6c91c0a839997c244de2ce0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b70789c43e3b36ec1b9e7175a22a1de4a6048656b4fbffcf02c7ed518d47b776 0.600000000000 1393746 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": 935740, "vin": [ { "gen": { "height": 935730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b70789c43e3b36ec1b9e7175a22a1de4a6048656b4fbffcf02c7ed518d47b776" } } ], "extra": [ 1, 129, 58, 110, 112, 3, 156, 25, 1, 219, 162, 160, 109, 61, 87, 67, 86, 1, 63, 210, 99, 47, 108, 145, 192, 168, 57, 153, 124, 36, 77, 226, 206, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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