Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36c5917a2fbb11e379934a425b46caab5b9bf97b0dbd86da40f52171f39a19b1

Tx prefix hash: 986343170dcf281a3b72d3885c06e2b5488a3ab9db23259781f6eff45f5918ee
Tx public key: 685714cc8367dba2d3e515a26c775a690f718d1c1d2de1cb9bee39f02189a745
Timestamp: 1712714325 Timestamp [UCT]: 2024-04-10 01:58:45 Age [y:d:h:m:s]: 01:015:02:23:31
Block: 997133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271768 RingCT/type: yes/0
Extra: 01685714cc8367dba2d3e515a26c775a690f718d1c1d2de1cb9bee39f02189a745021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aa2c0b75a8f1c06c0c991433bc850cb4651d3762516c01c2b432916c5475248 0.600000000000 1457561 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": 997143, "vin": [ { "gen": { "height": 997133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aa2c0b75a8f1c06c0c991433bc850cb4651d3762516c01c2b432916c5475248" } } ], "extra": [ 1, 104, 87, 20, 204, 131, 103, 219, 162, 211, 229, 21, 162, 108, 119, 90, 105, 15, 113, 141, 28, 29, 45, 225, 203, 155, 238, 57, 240, 33, 137, 167, 69, 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