Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 611a6223f9a8115d4262ae1fdbe04545a7a8caf5b8cdec981976c4d3cce9d1aa

Tx prefix hash: e80d346e8950eade80496250131b74a8e19ff076bf42c3e2abc1c75fb76602d5
Tx public key: b7d20c388591ac6db8ad0732e3223a92635de2d58a801d0a2a532c3db0310fba
Timestamp: 1700947095 Timestamp [UCT]: 2023-11-25 21:18:15 Age [y:d:h:m:s]: 01:089:19:08:50
Block: 899594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325301 RingCT/type: yes/0
Extra: 01b7d20c388591ac6db8ad0732e3223a92635de2d58a801d0a2a532c3db0310fba02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.641610737000 dcy

stealth address amount amount idx
00: 9d89d10361a18d5a1923e7b0591760898731e4077cbd2a4dd9f84f6b82ac2e96 0.641610737000 1356053 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": 899604, "vin": [ { "gen": { "height": 899594 } } ], "vout": [ { "amount": 641610737, "target": { "key": "9d89d10361a18d5a1923e7b0591760898731e4077cbd2a4dd9f84f6b82ac2e96" } } ], "extra": [ 1, 183, 210, 12, 56, 133, 145, 172, 109, 184, 173, 7, 50, 227, 34, 58, 146, 99, 93, 226, 213, 138, 128, 29, 10, 42, 83, 44, 61, 176, 49, 15, 186, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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