Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b301381af3cc9a9ae81a64371ac0fed30d6d8ba24dbecc52316d473396e14f6b

Tx prefix hash: 75749dab45f537c53d27cf71bf8951d1019a8bc089b75415608cb97d9c7b82cd
Tx public key: ac6f6a8f5f538424e9d39ed002a54d4a42f1f39f05344ab3c619abbada0ecc0b
Timestamp: 1705214008 Timestamp [UCT]: 2024-01-14 06:33:28 Age [y:d:h:m:s]: 01:086:10:51:59
Block: 934952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322893 RingCT/type: yes/0
Extra: 01ac6f6a8f5f538424e9d39ed002a54d4a42f1f39f05344ab3c619abbada0ecc0b02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55ea83b0fa5afb5ecaf2577f451a1a7d26ad4ebdbc1673afcdf24e95b97cc25c 0.600000000000 1392968 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": 934962, "vin": [ { "gen": { "height": 934952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55ea83b0fa5afb5ecaf2577f451a1a7d26ad4ebdbc1673afcdf24e95b97cc25c" } } ], "extra": [ 1, 172, 111, 106, 143, 95, 83, 132, 36, 233, 211, 158, 208, 2, 165, 77, 74, 66, 241, 243, 159, 5, 52, 74, 179, 198, 25, 171, 186, 218, 14, 204, 11, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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