Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b509280690ab7aed8e400f7fad229a90fad7e2643d41366dbe9e2e4cdbb2832b

Tx prefix hash: 506bb9f30bb8f005358eb48974d87c2f1862f2daa597ae6b8b9f8b62558a9e72
Tx public key: f3e7ad8ee861b1b8f8d6a46408d05c0223bd1bdc6b1bf83d8a65bc04e2413c72
Timestamp: 1733576683 Timestamp [UCT]: 2024-12-07 13:04:43 Age [y:d:h:m:s]: 00:113:13:26:29
Block: 1170012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80950 RingCT/type: yes/0
Extra: 01f3e7ad8ee861b1b8f8d6a46408d05c0223bd1bdc6b1bf83d8a65bc04e2413c72021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de9640c16cc3a9da47e9b6931ab93ed8417f5e844a8fd725cfb17e8e63c0241c 0.600000000000 1655739 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": 1170022, "vin": [ { "gen": { "height": 1170012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de9640c16cc3a9da47e9b6931ab93ed8417f5e844a8fd725cfb17e8e63c0241c" } } ], "extra": [ 1, 243, 231, 173, 142, 232, 97, 177, 184, 248, 214, 164, 100, 8, 208, 92, 2, 35, 189, 27, 220, 107, 27, 248, 61, 138, 101, 188, 4, 226, 65, 60, 114, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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