Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e03b4f4f2ee4f713bc076abcf8ea414044891bd5e3bbc4263a25284f80125b

Tx prefix hash: 676b475046039c9a3b0657eb5c89bdf895a442e9ddfc9f011e9e2609e2c5c11f
Tx public key: 7f979d3ecbe59f2160c27ed701f0c3fb38bbf65da40a835cf4df860ba423f23a
Timestamp: 1608507437 Timestamp [UCT]: 2020-12-20 23:37:17 Age [y:d:h:m:s]: 04:006:21:53:35
Block: 166090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1017757 RingCT/type: yes/0
Extra: 017f979d3ecbe59f2160c27ed701f0c3fb38bbf65da40a835cf4df860ba423f23a021100000046b9b01d0b000000000000000000

1 output(s) for total of 172.867395847000 dcy

stealth address amount amount idx
00: 43982d9aa0d35c78d2c27af1cf48b430cda8e2d8fd1f91d1e31ee6ec1b18c06b 172.867395847000 303399 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": 166100, "vin": [ { "gen": { "height": 166090 } } ], "vout": [ { "amount": 172867395847, "target": { "key": "43982d9aa0d35c78d2c27af1cf48b430cda8e2d8fd1f91d1e31ee6ec1b18c06b" } } ], "extra": [ 1, 127, 151, 157, 62, 203, 229, 159, 33, 96, 194, 126, 215, 1, 240, 195, 251, 56, 187, 246, 93, 164, 10, 131, 92, 244, 223, 134, 11, 164, 35, 242, 58, 2, 17, 0, 0, 0, 70, 185, 176, 29, 11, 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