Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0574a8bb82bd1ebc1b89ddf679e4e625a65aa2afe7f4681b5b10613611cfaab1

Tx prefix hash: 8066db49c75c0b88988cfbd2e68cf717a43a34e09ce94a258f7f50d2592956d9
Tx public key: 69421d21ea383bf2d15551a82dde52a4295dc3af133f6797b2f2c6bd5f69c8ec
Timestamp: 1675134711 Timestamp [UCT]: 2023-01-31 03:11:51 Age [y:d:h:m:s]: 02:281:06:58:07
Block: 686477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720385 RingCT/type: yes/0
Extra: 0169421d21ea383bf2d15551a82dde52a4295dc3af133f6797b2f2c6bd5f69c8ec021100000001835e4d22000000000000000000

1 output(s) for total of 3.261494586000 dcy

stealth address amount amount idx
00: fd14c3155a2894d4c306964e251397f83c56e580192301bd3992ead4b869dbf4 3.261494586000 1128970 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": 686487, "vin": [ { "gen": { "height": 686477 } } ], "vout": [ { "amount": 3261494586, "target": { "key": "fd14c3155a2894d4c306964e251397f83c56e580192301bd3992ead4b869dbf4" } } ], "extra": [ 1, 105, 66, 29, 33, 234, 56, 59, 242, 209, 85, 81, 168, 45, 222, 82, 164, 41, 93, 195, 175, 19, 63, 103, 151, 178, 242, 198, 189, 95, 105, 200, 236, 2, 17, 0, 0, 0, 1, 131, 94, 77, 34, 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