Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395f0e15476df7e6384ad91726e822d46ed800e885e47866b16796de0ef5ffc8

Tx prefix hash: dea731b78f910f8fcbeb927156562e3ddc664e0b0a8cb918a0deeba0c724d18a
Tx public key: 3c6d0d757f6b16849e91af09d20371618311a4b68eae5736f3bb3b7b1a7a5885
Timestamp: 1728549147 Timestamp [UCT]: 2024-10-10 08:32:27 Age [y:d:h:m:s]: 00:231:16:09:24
Block: 1128432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165409 RingCT/type: yes/0
Extra: 013c6d0d757f6b16849e91af09d20371618311a4b68eae5736f3bb3b7b1a7a5885021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fde11ff46323ce066dfb2b2f832a64ae0c3391e9b0d73797d9149e1eb864a58d 0.600000000000 1611251 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": 1128442, "vin": [ { "gen": { "height": 1128432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fde11ff46323ce066dfb2b2f832a64ae0c3391e9b0d73797d9149e1eb864a58d" } } ], "extra": [ 1, 60, 109, 13, 117, 127, 107, 22, 132, 158, 145, 175, 9, 210, 3, 113, 97, 131, 17, 164, 182, 142, 174, 87, 54, 243, 187, 59, 123, 26, 122, 88, 133, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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