Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1db2f97a87524fe41ee5db4594579665043ac4d07b1767d09e7d687ff426020

Tx prefix hash: 27bd865d746000e9c88c4614622cad24c7ee50f79ac1da5409bfac392366bf30
Tx public key: f5d0fdbadc9d4bd6fdfaf29085fb79335d3931c7acb0f960e204273d49d1fe6f
Timestamp: 1706636115 Timestamp [UCT]: 2024-01-30 17:35:15 Age [y:d:h:m:s]: 01:055:05:55:52
Block: 946743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300545 RingCT/type: yes/0
Extra: 01f5d0fdbadc9d4bd6fdfaf29085fb79335d3931c7acb0f960e204273d49d1fe6f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a89ec806203b9c69ee8f89ccf5b0dc78d36fc754d30e7c5db0d8e17fe256b441 0.600000000000 1405083 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": 946753, "vin": [ { "gen": { "height": 946743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a89ec806203b9c69ee8f89ccf5b0dc78d36fc754d30e7c5db0d8e17fe256b441" } } ], "extra": [ 1, 245, 208, 253, 186, 220, 157, 75, 214, 253, 250, 242, 144, 133, 251, 121, 51, 93, 57, 49, 199, 172, 176, 249, 96, 226, 4, 39, 61, 73, 209, 254, 111, 2, 17, 0, 0, 0, 7, 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