Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcd8b9fc9026a9610a2ef9bb4268fc56572536b306ea21b7cf71f3b0bd77721c

Tx prefix hash: 56f6c316c7543a35336ec4e3fd2c34f2df6661cdd45cef10cd0efa68f34434a0
Tx public key: 6be9f2c3a461c675812d2d804a7d1f690fd4eb8e2839d27b14c76cf91ead34fb
Timestamp: 1577769898 Timestamp [UCT]: 2019-12-31 05:24:58 Age [y:d:h:m:s]: 04:364:14:58:07
Block: 35484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149756 RingCT/type: yes/0
Extra: 016be9f2c3a461c675812d2d804a7d1f690fd4eb8e2839d27b14c76cf91ead34fb0211000000114943cd9f000000000000000000

1 output(s) for total of 468.195927909000 dcy

stealth address amount amount idx
00: 883c69614022b31a619a6ef682eacece1bdf8822ac9e8398d67ce38a82261a99 468.195927909000 59874 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": 35494, "vin": [ { "gen": { "height": 35484 } } ], "vout": [ { "amount": 468195927909, "target": { "key": "883c69614022b31a619a6ef682eacece1bdf8822ac9e8398d67ce38a82261a99" } } ], "extra": [ 1, 107, 233, 242, 195, 164, 97, 198, 117, 129, 45, 45, 128, 74, 125, 31, 105, 15, 212, 235, 142, 40, 57, 210, 123, 20, 199, 108, 249, 30, 173, 52, 251, 2, 17, 0, 0, 0, 17, 73, 67, 205, 159, 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