Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c370eacbccbe5c7f2bb633617f2e658114f536886a2617b109994181602b491d

Tx prefix hash: 525facfa9234e5c73f80ece4ca7f03ccce687b48d68f4104274eed9709f2a5e0
Tx public key: 7d37a93279e568d72c4a5e285b09e9571f5fa87e0d21affa0bc1fc400fd37dca
Timestamp: 1672270559 Timestamp [UCT]: 2022-12-28 23:35:59 Age [y:d:h:m:s]: 02:136:16:05:46
Block: 662705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 619410 RingCT/type: yes/0
Extra: 017d37a93279e568d72c4a5e285b09e9571f5fa87e0d21affa0bc1fc400fd37dca021100000003faf35c9c000000000000000000

1 output(s) for total of 3.910058013000 dcy

stealth address amount amount idx
00: 5ba135b32f7a40ac0024d8c3e5977d7d96b84f376695deded217f6b629e18d71 3.910058013000 1103570 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": 662715, "vin": [ { "gen": { "height": 662705 } } ], "vout": [ { "amount": 3910058013, "target": { "key": "5ba135b32f7a40ac0024d8c3e5977d7d96b84f376695deded217f6b629e18d71" } } ], "extra": [ 1, 125, 55, 169, 50, 121, 229, 104, 215, 44, 74, 94, 40, 91, 9, 233, 87, 31, 95, 168, 126, 13, 33, 175, 250, 11, 193, 252, 64, 15, 211, 125, 202, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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