Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ee9f697572f64a7194c1c771a0733ae2afd0c180cd9395fe4b2d1fb2700530

Tx prefix hash: f95dcf7935306abfbeb293702d7808c2dd72e5ba7a6be11203140c985255650d
Tx public key: b6fd6ade7b3ee9c9a1f6e4a2d701ccff70b4c4ac6e810a560609a0abbd1bea15
Timestamp: 1576643068 Timestamp [UCT]: 2019-12-18 04:24:28 Age [y:d:h:m:s]: 05:146:04:04:41
Block: 28042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1252433 RingCT/type: yes/0
Extra: 01b6fd6ade7b3ee9c9a1f6e4a2d701ccff70b4c4ac6e810a560609a0abbd1bea150211000000109159db1e000000000000000000

1 output(s) for total of 495.548400133000 dcy

stealth address amount amount idx
00: fd6dcb935250074a9aec9f0d088601a6a1aa6f103a323c7970f2e4ab5a281e06 495.548400133000 46564 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": 28052, "vin": [ { "gen": { "height": 28042 } } ], "vout": [ { "amount": 495548400133, "target": { "key": "fd6dcb935250074a9aec9f0d088601a6a1aa6f103a323c7970f2e4ab5a281e06" } } ], "extra": [ 1, 182, 253, 106, 222, 123, 62, 233, 201, 161, 246, 228, 162, 215, 1, 204, 255, 112, 180, 196, 172, 110, 129, 10, 86, 6, 9, 160, 171, 189, 27, 234, 21, 2, 17, 0, 0, 0, 16, 145, 89, 219, 30, 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