Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08eec9a9873fa8cfd0f1f93efa8b11002c7d030ac661997386eb36bff22f67d4

Tx prefix hash: 931149cb74b1d51758164c02803855b796f2ea0263ac51789099acfcccb319fe
Tx public key: 3b3091e8ce446a4bc92b81dc1aceac05ec2b64c97f09450dfaa41031ee6d4c62
Timestamp: 1703120816 Timestamp [UCT]: 2023-12-21 01:06:56 Age [y:d:h:m:s]: 01:102:06:23:58
Block: 917635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334193 RingCT/type: yes/0
Extra: 013b3091e8ce446a4bc92b81dc1aceac05ec2b64c97f09450dfaa41031ee6d4c62021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ebab9c5da32b0b778282fa1ed81b635a8b6a70c3bd6e3d5c99f2dcf60bef28b 0.600000000000 1375217 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": 917645, "vin": [ { "gen": { "height": 917635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ebab9c5da32b0b778282fa1ed81b635a8b6a70c3bd6e3d5c99f2dcf60bef28b" } } ], "extra": [ 1, 59, 48, 145, 232, 206, 68, 106, 75, 201, 43, 129, 220, 26, 206, 172, 5, 236, 43, 100, 201, 127, 9, 69, 13, 250, 164, 16, 49, 238, 109, 76, 98, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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