Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bb8df17ae7c25e15290ac7b08838cb5ab10fc9941f540ff6b6e4c50a48eaef0

Tx prefix hash: 6f5f77e86c76c1d4dab17c2f06d4d9667edaf2e90c7a13b94fa79bc0f5331f5a
Tx public key: 251b01fbfdfcb52e84109ec7262720a005124af71a140268676f31c4a7ef4836
Timestamp: 1705615730 Timestamp [UCT]: 2024-01-18 22:08:50 Age [y:d:h:m:s]: 00:358:21:54:29
Block: 938286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256955 RingCT/type: yes/0
Extra: 01251b01fbfdfcb52e84109ec7262720a005124af71a140268676f31c4a7ef48360211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f223d8d1a59f882b78d77989745f22a1bf3b1d65cb0df760ffbcf851af31c61 0.600000000000 1396356 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": 938296, "vin": [ { "gen": { "height": 938286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f223d8d1a59f882b78d77989745f22a1bf3b1d65cb0df760ffbcf851af31c61" } } ], "extra": [ 1, 37, 27, 1, 251, 253, 252, 181, 46, 132, 16, 158, 199, 38, 39, 32, 160, 5, 18, 74, 247, 26, 20, 2, 104, 103, 111, 49, 196, 167, 239, 72, 54, 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