Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70f130b5a7e66088b2ca4ab726c44c3b8a58ad722038d00efb93c9c156fde2c7

Tx prefix hash: fc20fa965808f628ea58100f2f9afbcc0b2e0a932783e98633a1d33bc682f3eb
Tx public key: 2bcb8f7868975abe48f3759eda8ed2a41b1fb636474a824ca5cfb2b6468d7605
Timestamp: 1726486202 Timestamp [UCT]: 2024-09-16 11:30:02 Age [y:d:h:m:s]: 00:072:23:21:52
Block: 1111331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52169 RingCT/type: yes/0
Extra: 012bcb8f7868975abe48f3759eda8ed2a41b1fb636474a824ca5cfb2b6468d7605021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb2b78091f9bdfd27258d18504e3c4bc3f9a2f171e916a6deedbd978af1e2971 0.600000000000 1590250 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": 1111341, "vin": [ { "gen": { "height": 1111331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb2b78091f9bdfd27258d18504e3c4bc3f9a2f171e916a6deedbd978af1e2971" } } ], "extra": [ 1, 43, 203, 143, 120, 104, 151, 90, 190, 72, 243, 117, 158, 218, 142, 210, 164, 27, 31, 182, 54, 71, 74, 130, 76, 165, 207, 178, 182, 70, 141, 118, 5, 2, 17, 0, 0, 0, 7, 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