Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd7eee7e46212608cc84bf5a84e640b45f9e647e9d18115b3c4a00055552757

Tx prefix hash: 3acfae8acbb98046b04e5a14310ac23b04024f25c28183e7e432cde95942ab9e
Tx public key: f3feaa3719b202fa319cf01c00f39b61c5b1418948dc032ec8d9d42a2b3a3781
Timestamp: 1724535200 Timestamp [UCT]: 2024-08-24 21:33:20 Age [y:d:h:m:s]: 00:289:20:00:27
Block: 1095177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207036 RingCT/type: yes/0
Extra: 01f3feaa3719b202fa319cf01c00f39b61c5b1418948dc032ec8d9d42a2b3a3781021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 076ac98bcd93a6bd25a24c446e97952f25c0ebb61d234f2f5fa67fd81e78e0f3 0.600000000000 1570326 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": 1095187, "vin": [ { "gen": { "height": 1095177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "076ac98bcd93a6bd25a24c446e97952f25c0ebb61d234f2f5fa67fd81e78e0f3" } } ], "extra": [ 1, 243, 254, 170, 55, 25, 178, 2, 250, 49, 156, 240, 28, 0, 243, 155, 97, 197, 177, 65, 137, 72, 220, 3, 46, 200, 217, 212, 42, 43, 58, 55, 129, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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